-
-
Notifications
You must be signed in to change notification settings - Fork 67
Display command text in tool_call fragments #229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
When ACP sends tool_call updates, the command from rawInput.command is stored but only used for transcript logging. This change prepends the command to the body when rendering tool_call_update fragments, so users can see what command was executed. Before: Only title, status, and output shown After: Shows '$ <command>' above the output (styled as comment)
1. Show command in permission dialogs 2. Upgrade section titles when command is known
|
Thanks for the PR!
Ah interesting. Looks like Copilot isn't including the command in the title (also noticed missing from permission dialog), which I've found in some of the other agents. Couple of examples: Gemini
Gemini ACP traffic
Claude
Claude ACP traffic
Copilot
Copilot ACP traffic
Copilot fix (please try)I've submitted a fix for Copilot in ded0a5e so it displays commands in permission dialogs as well as promotes section titles to include command. Could you give that a try and see if that works for you? You'll need to update to v0.31.3. This is what it should look like
|
|
Thanks I'll try tomorrow. BTW I work at GitHub and am currently submitting a PR to enhance the title fields Copilot sends, so there might be clashing behavior :) |
Great! The bit I added attempts to include the command if not already in title, so hopefully no clashing, but please shout if that's not the case.
Lovely! Any chance you can get your employer to sponsor this project so I can make the work sustainable? It's taken quite a bit of effort to get agent-shell to where it is today (including dependencies like acp.el and shell-maker). More specifically, I've been adding and improving Copilot support (1, 2, 3, 4, 5). Lastly, as an indie dev, I have more flexibility/time to bring these tools to felllow emacsers, but sponsorships are an important piece to me to make this kind of work sustainable. |
|
So I'm going to be offline for about a week but will follow up. Followed you on Bluesky if you want to chat. Really appreciate all your work, very intersectional with my interests too! |
Great to hear. Will reach out there!
Hope all's well and you get some nice time off! |









Problem
When ACP sends
tool_callupdates, agent-shell stores the command (fromrawInput.command) but never displays it in the UI. Only the title, status, and output are shown. This means users don't see what command was executed—just the result.Compare to Copilot CLI which shows:
agent-shell currently shows only the title and output, missing the
$ find...line.Root cause
In
agent-shell.el, the command is stored at line 813:But in the
tool_call_updatehandler (~line 974), only the body text is passed without the command:The
:commandis used only for transcript logging (line 955), not UI display.Fix
Prepend the command to the body when rendering tool_call_update fragments:
Testing
Tested with Copilot CLI via ACP. Tool calls now display the command above the output, styled as a comment.